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
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (8y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- teepublic.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-07-19 06:05 UTC
- Forward DNS last checked
- 2026-07-19 06:05 UTC
Forward DNS records for teepublic.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 13.35.78.4 | — | 172800s |
| A | 13.35.78.51 | — | 172800s |
| A | 13.35.78.56 | — | 172800s |
| A | 13.35.78.72 | — | 172800s |
| MX | alt1.aspmx.l.google.com | 5 | — |
| MX | alt2.aspmx.l.google.com | 5 | — |
| MX | aspmx.l.google.com | 1 | — |
| MX | aspmx2.googlemail.com | 10 | — |
| MX | aspmx3.googlemail.com | 10 | — |
| NS | ns-1128.awsdns-13.org | — | — |
| NS | ns-1947.awsdns-51.co.uk | — | — |
| NS | ns-397.awsdns-49.com | — | — |
| NS | ns-975.awsdns-57.net | — | — |
| TXT | 8DB69E7E64 | — | — |
| TXT | 97b5960f2a1f4d6298203eb03fce7ffa | — | — |
| TXT | MS=ms56202852 | — | — |
| TXT | anthropic-domain-verification-v9rcaf=vXRVREpEOUOtqquYbFaGtkBBF | — | — |
| TXT | atlassian-domain-verification=QXMXSt1Y5pkY3LHuPAvUx0m/baw85nW1IGHuwcRXDSMNAoDAm3dv0ko0LoZwfdKt | — | — |
| TXT | ca3-e6946320ec1c4af6ab095c8475f70750 | — | — |
| TXT | ca3-ef67b0f7ff5d45458cea21035d6de6ff | — | — |
| TXT | facebook-domain-verification=79jqwk922h22fg6gfazjyepjgfkkhp | — | — |
| TXT | figma-domain-verification=857b7e32775a5e08d9dc9f0e88cb2eb2351cca3414882df32cf12769f8652ce0-1760470107 | — | — |
| TXT | globalsign-domain-verification=497A803718A2F44B8247FB306A6F06D2 | — | — |
| TXT | google-site-verification=JC7sVUYESGyMT7PH2fj4iEOMNRVc3ZIl0bdatBYfR6s | — | — |
| TXT | google-site-verification=galmAnC3ewJJdwVj8M7pzmg_OOEaQve5pM2jdNm80Ps | — | — |
| TXT | google-site-verification=hhtRuVkI7v71wbb6Kvd_lJ6pLwnr4my5LFlTwX8kszw | — | — |
| TXT | google-site-verification=y7ai41vhRwqd65ZxE1RPgLB2De0pTWuXUGR8mXSewTM | — | — |
| TXT | google-site-verification=zv0PYgqCy2s5lvk9BwoHF0c4mcNmGcl83p2nd-A_dQs | — | — |
| TXT | have-i-been-pwned-verification=176e0c13eaf6c3ba63909a690bdd6b86 | — | — |
| TXT | heroku-domain-verification=b6jsxhkbhqkknvhkm6pbezbqfcl6c99z8mmvfzp4oqg | — | — |
| TXT | pw3ntlxrh9251zslw4tpv8gfgf0qt7r3 | — | — |
| TXT | stripe-verification=033C589D056CE6626F45A55C39ADA2D8F5475E6D8F85C83D925CEC325BE6A1D9 | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:dmarc-reports@teepublic.com; ruf=mailto:dmarc-reports@teepublic.com; fo=1; | — | — |
| TXT | v=spf1 include:mktomail.com include:aspmx.sailthru.com include:_spf.google.com ~all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 209.127.62.134
- CIDR range
- 209.127.62.0/24
- IP range (int)
- 3,514,777,088 — 3,514,777,343
- Prefix length
- /24
- Location
- Halfweg, North Holland, The Netherlands
- Coordinates
- 43.631900, -79.371600
- Accuracy radius
- 1000 km
- Postal code
- 1165
- Regional Internet Registry
- ARIN
- Allocated
- 2018-01-12
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite
- Last updated
- 2026-06-21 06:18:58
Frequently Asked Questions
Who owns 209.127.62.134?
209.127.62.134 is allocated to an unknown organization, registered in Halfweg, The Netherlands.
Where is 209.127.62.134 located?
The geolocation for 209.127.62.134 maps to Halfweg, The Netherlands 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.127.62.134 on?
209.127.62.134 belongs to the 209.127.62.0/24 network block. This range contains 256 addresses.
Does 209.127.62.134 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.
