122.163.127.14
IP Intelligence Dossier
Your IP: 216.73.216.123
🏢 Ownership & Registration
| Organization | Network Administrator for ABTS DEL |
| ASN | AS24560 |
| Network Name | — |
| CIDR Block | — |
| RIR | APNIC |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | abts-north-dynamic-014.127.163.122.airtelbroadband.in |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | abts-north-dynamic-014.127.163.122.airtelbroadband.in |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web Server |
| HTTP Title | — |
| SSH Version | SSH-2.0-WeOnlyDo 2.6.1 |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=192.168.168.168, OU=HTTPS Management Certificate for SonicWALL (self-signed), O=HTTPS Management Certificate for SonicWALL (self-signed), L=Sunnyvale, S=California, C=US
Issued by CN=192.168.168.168, OU=HTTPS Management Certificate for SonicWALL (self-signed), O=HTTPS Management Certificate for SonicWALL (self-signed), L=Sunnyvale, S=California, C=US
Self-signed: Yes
| SANs | None |
| Valid From | 1970-01-01T00:00:01+00:00 |
| Valid Until | 2038-01-19T03:14:07+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 24855 days |
| Serial Number | 7393042F5BD056482C63A76A66AD5AE734DED747 |
| Thumbprint | D5CE7BAC6BE19F4C14D30F6E50D332DF93CEEC78 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 24% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 31% | 2 | 4 |
| ownership | 20% | 2 | 3 |
| reputation | 21% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 22% | 10 | 16 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mixed Signals (68%) — 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Geo sources disagree on country: US, IN
⚠ TLS certificate claims US but primary geo says IN
⚠ TLS certificate claims US but primary geo says IN
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:36 UTC |
| Last Seen | 2026-06-26 18:10:32 UTC |
| Profile Built | 2026-06-22 12:11:01 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 23 |
🔍 20 signal types · 23 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.