179.61.154.36
IP Intelligence Dossier
Your IP: 216.73.216.5
🏢 Ownership & Registration
| Organization | IPXO-MNT |
| ASN | AS269070 |
| Network Name | NET-179-61-154-0-24 |
| CIDR Block | 179.61.154.0/24 |
| RIR | LACNIC |
| Country | EU |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | Apache |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u7 |
🔐 TLS Certificate
An expired certificate for
E=suporte@172.31.255.2, CN=172.31.255.2, OU=SISTEMA MK-AUTH, O=MK-AUTH, L=CE, S=Fortaleza, C=BR was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.E=suporte@172.31.255.2, CN=172.31.255.2, OU=SISTEMA MK-AUTH, O=MK-AUTH, L=CE, S=Fortaleza, C=BR
Issued by E=suporte@172.31.255.2, CN=172.31.255.2, OU=SISTEMA MK-AUTH, O=MK-AUTH, L=CE, S=Fortaleza, C=BR
Self-signed: Yes
| SANs | None |
| Valid From | 2015-04-17T02:57:54+00:00 |
| Valid Until | 2025-04-14T02:57:54+00:00 (expired) |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha1RSA |
| Validity Period | 3650 days |
| Serial Number | 00C9D0E4A812CCBD2F |
| Thumbprint | B2C90C823C1FA6FFDDECC6F6E621B3EA0012C41A |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 2 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 25% | 1 | 1 |
| geolocation | 0% | 0 | 0 |
| Overall | 18% | 5 | 5 |
Coverage: 4/6 dimensions · Data sufficiency: partial
| Data Coherence | Contradictory (48%) — 3 contradiction(s) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
⚠ Geo sources disagree on country: BR, US, AE
⚠ TLS certificate claims BR but primary geo says AE
⚠ Geo sources disagree on country: BR, US, AE
⚠ TLS certificate claims BR but primary geo says AE
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-28 22:22:02 UTC |
| Last Seen | 2026-07-30 18:56:11 UTC |
| Profile Built | 2026-07-30 19:08:35 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 20 |
🔍 20 signal types · 20 observations collected
This report is generated from 20+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
ℹ️ About This Report
All data shown is publicly available network metadata — IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.