🌐 ammega.com
DOMAIN
· host
ammega.com
· threat 0.00 (UNTRACKED)
Not tracked as a local indicator — DNS / WHOIS / subdomains below still resolve from local caches where available.
Threat score
—
untracked
Sightings
—
0 sources
Subdomains (local)
0
from indicators
Related IPs
4
A/AAAA records
DNS records (local)
0
0 types
Reporting sources
0
0 enrichments
📡 Reporting-source breakdown
No data.
0 total source links on this indicator.
🏷 Tag breakdown (domain family)
No data.
📈 DNS record-type counts
No data.
📅 First-seen timeline (family)
No data.
🏷 WHOIS / Registration (local cache)
No cached WHOIS for ammega.com. Resolve & cache.
🏷 Tags
No tags on this indicator.
📡 DNS Records
Live (DNS-over-HTTPS · optional augmentation)
| Type | Value | TTL |
|---|---|---|
| A | 104.20.32.4 |
300 |
| A | 172.66.173.132 |
300 |
| AAAA | 2606:4700:10::6814:2004 |
300 |
| AAAA | 2606:4700:10::ac42:ad84 |
300 |
| MX | 0 ammega-com.mail.protection.outlook.com. |
300 |
| NS | lily.ns.cloudflare.com. |
21600 |
| NS | rodrigo.ns.cloudflare.com. |
21600 |
| TXT | Vkl-JX2-zlb |
300 |
| TXT | _globalsign-domain-verification=AufPn5mHfWR0GpyUOLa80nTVmOkUPleorEckvEf3WM |
300 |
| TXT | apple-domain-verification=5sVTvY2c9TlfCbvR |
300 |
| TXT | ms-domain-verification=9cb415ce-0266-4e65-8b69-25be7ea3020f |
300 |
| TXT | v=spf1 mx a include:spf.protection.outlook.com include:et._spf.pardot.com include:spf1.ammega.info include:spforacle.ammega.info include:_spf.salesforce.com ip4:207.211.63.183 ip4:208.116.180.100 ip4:208.116.180.104 ip4:162.218.1.205 ip4:162.218.1.206 ip4:162.218.1.150 ip4:162.218.0.230 ip4:54.240.57.47 ip4:54.240.57.46 ip4:68.179.109.125 ip4:40.107.6.49 ip4:80.197.60.32/29 ip4:154.14.55.140 ip4:69.174.127.2 ip4:14.201.108.59 ip4:123.243.157.179 ip4:123.243.64.43 ip4:27.33.174.170 ip4:60.240.234.251 ip4:14.200.111.59 ip4:192.200.190.165/30 ip4:104.195.80.16/28 ip4:192.200.181.144/28 ip4:174.37.85.64/28 ip4:75.126.150.248/30 ip4:63.141.144.128/28 ip4:104.195.127.0/28 -all |
300 |
| TXT | MS=ms69889785 |
300 |
| TXT | ciscocidomainverification=46668d019bd38a78b6cb40a62a536d1c71f82d99d86ecbb315172aa6fbbd1825 |
300 |
| TXT | pardot854583=8835b7f7c13ca7461956ac46871cd3650888fa74c5f567206658d8362b5f7bda |
300 |
| TXT | google-site-verification=H911zkTehLlXUsD-WQ30GCJ912C5MciTqRQ692Feu14 |
300 |
| TXT | MS=270A4BBB505A6984F69DD2BA7B1A14203AA9D367 |
300 |
| TXT | da2c3b371f25366ad847dd0d78a0e67f6e70ce64e6e759514b |
300 |
🖥 Related IPs (4)
Resolved from local A/AAAA records (augmented with live DoH when reachable). Each pivots to its IP dossier.
🌐 Subdomains — local intel (0)
No subdomains of ammega.com in local intel. Check crt.sh ↗
📡 Reporting Sources (0)
| Not in local DB, or no sources linked. |
🌐 Same-ASN domains (0)
No ASN linkage in local intel.
🔍 OSINT pivots — external lookups
🔗 Internal pivots & actions
📁 Case Management
Every panel resolves local-first: threat, category, first-seen & sightings from
indicators; DNS from dns_records; WHOIS from whois_cache; subdomains via bounded suffix match on indicators; related IPs from A/AAAA records; tags, reporting sources and the link graph from the local relations. Live OTX pulses and DNS-over-HTTPS are optional augmentation and their absence never blanks the dossier.
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Audit DNS to build passive history
- Pivot resolved IPs to their dossiers
- Report phishing to registrar/host