Hostname
catedralfmsp.com
Last fetched
catedralfmsp.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
catedralfmsp.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.32.241.10 | 13.32.241.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.32.241.35 | 13.32.241.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.32.241.45 | 13.32.241.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.32.241.62 | 13.32.241.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.252.39 | 3.169.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.252.48 | 3.169.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.252.49 | 3.169.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.169.252.58 | 3.169.252.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of catedralfmsp.com owner
- Contact emails
Subdomains
2 observed subdomains of catedralfmsp.com.
Web-graph footprint
Distinct hostnames that link to or from catedralfmsp.com in the public web crawl.
14 sites link to this hostname.
14 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for catedralfmsp.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | minhawebradio.net |
| SPF_MX | catedralfmsp.com |
Related pages
Pivot deeper into the graph from catedralfmsp.com.
- IP · 13.32.241.10
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · registro@brlogic.com
- TLD · .com
- Browse hostnames · ca…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "catedralfmsp.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.