Hostname
lemontaps.com
Last fetched
lemontaps.com resolves to 8 IPv4 addresses operated by AS35708 in BR. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
lemontaps.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.158.194.101 | 0.0.0.0/0 | AS35708 | — | BR |
| 108.158.194.12 | 0.0.0.0/0 | AS35708 | — | BR |
| 108.158.194.50 | 0.0.0.0/0 | AS35708 | — | BR |
| 108.158.194.56 | 0.0.0.0/0 | AS35708 | — | BR |
| 13.225.134.109 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.40 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.73 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.81 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of lemontaps.com owner
- Contact emails
- gdpr-masking@gdpr-masked.com
- 06347fa6-9f92-4f41-9e8b-89c433280fd3@identity-protect.org
- 9fa2621d-438e-40ea-8fbd-b459483d6276@identity-protect.org
- a03f3a46-f6c1-4332-870b-1595950df9a6@identity-protect.org
- ba053ac3-9f65-42c5-9044-d55ffeb4e234@identity-protect.org
- d0cb5d61-4e1f-454f-aebd-6c152228d7fc@identity-protect.org
- owner-2124688@lemontaps.com.whoisprivacyservice.org
Subdomains
30 observed subdomains of lemontaps.com.
Showing 20 of 30. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from lemontaps.com in the public web crawl.
57 sites link to this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for lemontaps.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | email.chargebee.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.profiprint.de |
Related pages
Pivot deeper into the graph from lemontaps.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "lemontaps.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.