209.208.2.151
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 (28y) +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)
- mta.email-services.atlantic.net
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 120 s
- Reverse DNS last checked
- 2026-11-03 03:36 UTC
Forward DNS records for mta.email-services.atlantic.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 209.208.2.151 | — | 120s |
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 UTC0
issued.live's latest DNS data shows no domain resolving to this IP.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- mta.email-services.atlantic.net — Nov 3, 2026 → present
- mta03.email-services.atlantic.net — Nov 1, 2026 → Nov 3, 2026
- mta.email-services.atlantic.net — Oct 30, 2026 → Nov 1, 2026
- mta01.email-services.atlantic.net — Oct 29, 2026 → Oct 30, 2026
- mta02.email-services.atlantic.net — Oct 28, 2026 → Oct 29, 2026
- mta.email-services.atlantic.net — Oct 25, 2026 → Oct 28, 2026
- mta02.email-services.atlantic.net — Oct 23, 2026 → Oct 25, 2026
- mta.email-services.atlantic.net — Oct 17, 2026 → Oct 23, 2026
- mta01.email-services.atlantic.net — Oct 15, 2026 → Oct 17, 2026
- mta02.email-services.atlantic.net — Oct 13, 2026 → Oct 15, 2026
- mta03.email-services.atlantic.net — Oct 10, 2026 → Oct 13, 2026
- mta01.email-services.atlantic.net — Oct 9, 2026 → Oct 10, 2026
- mta02.email-services.atlantic.net — Oct 8, 2026 → Oct 9, 2026
- mta01.email-services.atlantic.net — Oct 5, 2026 → Oct 8, 2026
- mta02.email-services.atlantic.net — Oct 4, 2026 → Oct 5, 2026
- mta03.email-services.atlantic.net — Oct 2, 2026 → Oct 4, 2026
- mta02.email-services.atlantic.net — Sep 30, 2026 → Oct 2, 2026
- mta03.email-services.atlantic.net — Sep 29, 2026 → Sep 30, 2026
- mta.email-services.atlantic.net — Sep 27, 2026 → Sep 29, 2026
- mta03.email-services.atlantic.net — Sep 24, 2026 → Sep 27, 2026
- mta01.email-services.atlantic.net — Aug 24, 2026 → Sep 24, 2026
- mta02.email-services.atlantic.net — Aug 17, 2026 → Aug 24, 2026
- mta03.email-services.atlantic.net — Jun 12, 2026 → Aug 17, 2026
Network Allocation for 209.208.2.151
- CIDR range
- 209.208.0.0/20
- IP range (int)
- 3,520,069,632 — 3,520,073,727
- Prefix length
- /20
- Organization
- Atlantic.net, Inc.
- ASN
- AS6364
- ASN name
- Atlantic.net, Inc.
- Location
- Orlando, Florida, United States
- Coordinates
- 28.550400, -81.183300
- Accuracy radius
- 10 km
- Postal code
- 32828
- Regional Internet Registry
- ARIN
- Allocated
- 1998-04-13
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-11-03 04:10:54
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 209.208.2.151?
209.208.2.151 is allocated to Atlantic.net, Inc. (AS6364), registered in Orlando, United States.
Where is 209.208.2.151 located?
The geolocation for 209.208.2.151 maps to Orlando, 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 209.208.2.151 on?
209.208.2.151 belongs to the 209.208.0.0/20 network block announced by AS6364. This range contains 4,096 addresses.
Does 209.208.2.151 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.
