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 (25y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- egmont.pl
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 14400 s
- Reverse DNS last checked
- 2026-09-23 10:53 UTC
- Forward DNS last checked
- 2026-09-23 10:53 UTC
Forward DNS records for egmont.pl
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 185.135.90.41 | — | 172800s |
| MX | egmont-pl.mail.protection.outlook.com | 1 | — |
| NS | desi.ns.cloudflare.com | — | — |
| NS | lex.ns.cloudflare.com | — | — |
| TXT | 2617b2c4761ea33e346dfd2ad50df8ca5f79c7fbe43df6925e8ac79c9f291878 | — | — |
| TXT | MS=ms65972978 | — | — |
| TXT | adi8r5j2upgatdha57tje0r8ii | — | — |
| TXT | d97nequ146sa7qeqghsm9r6gen | — | — |
| TXT | dropbox-domain-verification=an5jhbpuko01 | — | — |
| TXT | mojecertpl-site-verification-mPH6GbPvIgKzkQTnNDfweG42ZYUTwSFv | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:a1d4951bf4fb930@rep.dmarcanalyzer.com; ruf=mailto:a1d4951bf4fb930@for.dmarcanalyzer.com; sp=none; fo=1; | — | — |
| TXT | v=spf1 include:spf1.egmont.com include:_spf.redlink.pl mx:mail.egmont.com mx:sq7ro.net ip4:194.0.167.110/32 -all | — | — |
| CAA | issue certum.pl | 0 | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue godaddy.com | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild certum.pl | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild godaddy.com | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 80.72.33.118
- CIDR range
- 80.72.32.0/20
- IP range (int)
- 1,346,904,064 — 1,346,908,159
- Prefix length
- /20
- Organization
- eTOP sp. z o.o.
- ASN
- AS20853
- ASN name
- eTOP sp. z o.o.
- Location
- Poland
- Coordinates
- 52.239400, 21.036200
- Accuracy radius
- 200 km
- Regional Internet Registry
- RIPE
- Allocated
- 2001-06-08
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-11 00:20:09
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 80.72.33.118?
80.72.33.118 is allocated to eTOP sp. z o.o. (AS20853), registered in Poland.
Where is 80.72.33.118 located?
The geolocation for 80.72.33.118 maps to Poland 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 80.72.33.118 on?
80.72.33.118 belongs to the 80.72.32.0/20 network block announced by AS20853. This range contains 4,096 addresses.
Does 80.72.33.118 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.
