130.14.16.110
Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Long-established allocation (38y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- nlm.nih.gov
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-11-04 04:31 UTC
Forward DNS records for nlm.nih.gov
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 130.14.16.110 | — | 3600s |
| AAAA | 2607:f220:41e:1016::110 | — | 3229s |
| MX | nihcesxway3.hub.nih.gov | 10 | — |
| MX | nihcesxway4.hub.nih.gov | 10 | — |
| MX | nihcesxway5.hub.nih.gov | 10 | — |
| MX | nihcesxway6.hub.nih.gov | 10 | — |
| MX | nihcesxwayst03.hub.nih.gov | 10 | — |
| MX | nihcesxwayst04.hub.nih.gov | 10 | — |
| MX | nihcesxwayst05.hub.nih.gov | 10 | — |
| MX | nihcesxwayst06.hub.nih.gov | 10 | — |
| NS | lhcns1.nlm.nih.gov | — | — |
| NS | lhcns2.nlm.nih.gov | — | — |
| NS | ns.nih.gov | — | — |
| NS | ns2.nih.gov | — | — |
| NS | ns3.nih.gov | — | — |
| TXT | A/aHTj2IRR3m37p7zSqMJM97lYQAyAkV78zyIJgqM8MlS/mw1mqS1C6DS/qEOYMId66sc+2U9PeQ8b1AXkEQMw== | — | — |
| TXT | _4fgf9wsjuk5k41t6kzlg3bzcu1p72dj | — | — |
| TXT | _d1fmnw6ms87whm9ew41pbgj4zyzbao1 | — | — |
| TXT | _g3gczfjzmvi5vum7d0i95nvllimb284 | — | — |
| TXT | amazonses:oqFwg1Ruks+2BtoQfoQ73XwgaCHjh29zJiAUJqJZ9Ig= | — | — |
| TXT | google-site-verification=k9misalwdj0eJ1c01_rQqoYwHIWkV1vFoQmgXkgTghw | — | — |
| TXT | v=spf1 include:amazonses.com include:nih.gov ~all | — | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue amazonaws.com | 0 | — |
| CAA | issue amazontrust.com | 0 | — |
| CAA | issue awstrust.com | 0 | — |
| CAA | issue digicert.com | 0 | — |
| CAA | issue godaddy.com | 0 | — |
| CAA | issue identrust.com | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issuewild amazon.com | 0 | — |
| CAA | issuewild amazonaws.com | 0 | — |
| CAA | issuewild amazontrust.com | 0 | — |
| CAA | issuewild awstrust.com | 0 | — |
| CAA | issuewild digicert.com | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-11-04 UTC2
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Network Allocation for 130.14.16.110
- CIDR range
- 130.14.0.0/19
- IP range (int)
- 2,181,955,584 — 2,181,963,775
- Prefix length
- /19
- Organization
- National Library of Medicine
- ASN
- AS70
- ASN name
- National Library of Medicine
- Location
- Gaithersburg, Maryland, United States
- Coordinates
- 39.109000, -77.248900
- Accuracy radius
- 50 km
- Postal code
- 20878
- Regional Internet Registry
- ARIN
- Allocated
- 1988-04-19
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-11-03 04:09:06
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 130.14.16.110?
130.14.16.110 is allocated to National Library of Medicine (AS70), registered in Gaithersburg, United States.
Where is 130.14.16.110 located?
The geolocation for 130.14.16.110 maps to Gaithersburg, United States based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 130.14.16.110 on?
130.14.16.110 belongs to the 130.14.0.0/19 network block announced by AS70. This range contains 8,192 addresses.
Does 130.14.16.110 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
