Hostname
pomelocard.com
Last fetched
pomelocard.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in IT. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
pomelocard.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 |
|---|---|---|---|---|
| 108.156.2.16 | 108.156.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.156.2.3 | 108.156.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.156.2.47 | 108.156.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 108.156.2.75 | 108.156.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IT |
| 13.227.185.13 | 13.227.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | VN |
| 13.227.185.25 | 13.227.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | VN |
| 13.227.185.81 | 13.227.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | VN |
| 13.227.185.82 | 13.227.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | VN |
WHOIS identity
- Registrar
- iana:1068
- Organization
- itzik parnafes
- Contact emails
Subdomains
10 observed subdomains of pomelocard.com.
Web-graph footprint
Distinct hostnames that link to or from pomelocard.com in the public web crawl.
6 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for pomelocard.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf.mandrillapp.com |
Related pages
Pivot deeper into the graph from pomelocard.com.
- IP · 108.156.2.16
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1068
- Country · IT
- Email · itzikpa@payoneer.com
- TLD · .com
- Browse hostnames · po…
- 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: "pomelocard.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.