Skip to content

Hostname

oshdelmar.com

Last fetched

oshdelmar.com resolves to 104.21.32.242, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. oshdelmar.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:51:25 GMT
Last seen on a feed
Sun, 13 Sep 2026 00:52:19 GMT

Nutrition Label

WHISPER CANON · oshdelmar.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency6.7/10Resolver footprint4.6/10canon.whisper.security/host/oshdelmar.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
wildcard.oshdelmar.com
www.oshdelmar.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • meiling.ns.cloudflare.com
  • razvan.ns.cloudflare.com
  • theo.ns.cloudflare.com
  • zariyah.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • 7yccnpv4s4d3ge257ekqeaynkzmskimx5qxbvwyv3p3v7em2dqdq.mx-verification.google.com

SPF policy

  • ip: 51.254.104.0/24
  • ip: 45.150.109.0/24
  • ip: 167.148.115.0/24
  • ip: 185.28.119.0/24
  • ip: 213.109.147.0/24
  • ip: 45.143.166.0/24
  • ip: 5.196.169.0/24
  • ip: 167.148.185.0/24
  • ip: 185.130.212.0/24
  • ip: 81.31.213.0/24
  • ip: 91.236.230.0/24
  • ip: 31.56.236.0/24
  • ip: 45.66.249.0/24
  • ip: 212.8.251.0/24
  • ip: 146.19.254.0/24
  • ip: 98.159.35.0/24
  • ip: 85.239.53.0/24
  • ip: 173.244.60.0/24
  • ip: 62.106.66.0/24
  • ip: 141.105.67.0/24
  • ip: 146.255.85.0/24
  • ip: 64.64.97.0/24

Threat-feed evidence

History

Related pages

Pivot from oshdelmar.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "oshdelmar.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.