How we verify DFW properties and rental listings

Every verdict on this site traces back to a named public source or a check you could repeat yourself. This page lists each signal we actually run, what it catches, and where it can be wrong.

RemotePropView Research Team

Dallas-based analysts at Goals and Gambles LLC. Every claim is tied to a primary source and checked against our editorial standards and verification methodology.

Last reviewed July 2026

The rule behind everything below: a missing check is never a passed check. When a source is down or has no data we say "could not verify", and no single soft signal ever produces a scam verdict on its own.

County appraisal record

Source: Live parcel lookups against the Dallas (DCAD), Tarrant (TAD), Collin (CCAD), and Denton (DCAD) central appraisal district public records.
What it catches: Invented addresses (no parcel exists), fake ownership claims, and inflated value claims. If the county has never heard of an address, that is a hard signal.
Honest limits: Multi-unit buildings can share one street address across many parcels; when county records disagree on the owner we say "no record" rather than guess. Brand-new construction may not have a parcel yet.

Owner-of-record match

Source: The name on the listing or message is compared against the county appraisal owner of record (live CAD lookup, with a licensed property-data fallback).
What it catches: The classic fake-landlord scam: a "building manager" collecting deposits for a property owned by someone who has never heard of them.
Honest limits: Legitimate owners use LLCs, trusts, and property managers, so a name mismatch alone is never called proof of fraud - we show the mismatch and tell you to verify.

Address existence (map resolution + county cross-check)

Source: Geocoding resolution level (does the street and number actually resolve, or only the ZIP code area?) cross-checked against county parcel records.
What it catches: Fully invented street addresses. We only reject an address when two independent sources agree it does not exist; if either source errors, we let it through and keep checking.
Honest limits: Rural and very new streets can be missing from map data. That is why a single source is never enough to reject.

Street View existence and capture date

Source: Google Street View imagery metadata (the free metadata endpoint, not the image itself).
What it catches: Confirms a real, photographed place and shows when it was last photographed. A street that maps resolve but no camera has ever driven is worth a closer look.
Honest limits: Coverage gaps exist, especially on new streets and private roads, so "never photographed" is a warning, not a verdict. We only run this check when the street itself resolves, because the metadata service otherwise reports the nearest panorama instead of the address.

Community scam blocklist

Source: Phone numbers, emails, and URLs reported by renters and confirmed by moderators, fed by every scam check run on the site.
What it catches: Repeat offenders instantly. A contact already confirmed as a scammer is flagged before any other check runs.
Honest limits: Community reports can be wrong or malicious, so raw reports are weighted differently from moderator-confirmed entries, values are masked publicly, and anyone can dispute a listing.

Contact reputation (phone, email, URL)

Source: Third-party fraud intelligence (line type, VOIP detection, abuse history, phishing and malware flags) when available.
What it catches: Burner VOIP numbers, addresses with recent fraud reports, and malicious listing links.
Honest limits: When the third-party service is unavailable we say "could not fully verify" rather than pretending the check passed.

Disposable email detection

Source: A curated list of throwaway email providers, checked locally.
What it catches: Contacts using 10-minute burner inboxes - a strong scam signal that costs nothing to check.
Honest limits: New burner domains appear constantly; the list catches the common ones, not all of them.

Listing site domain age

Source: Registry RDAP records (the successor to WHOIS) for the domain behind a listing link.
What it catches: Scam sites registered days before the campaign. A "property management company" whose website is 3 weeks old gets flagged.
Honest limits: Old domains get compromised too, and legitimate businesses launch new sites - age is one signal among many.

Listing photo analysis

Source: AI vision analysis of listing photos plus perceptual fingerprinting of images from confirmed scam listings.
What it catches: AI-generated property photos and images reused from previously reported scam listings.
Honest limits: A real photo can be stolen from a legitimate listing, and detection of AI imagery is probabilistic - we report likelihood, not certainty.

Message pattern analysis

Source: Deterministic checks for known scam language: wire-transfer demands, overseas-owner stories, deposits before viewing, pressure to act fast.
What it catches: The scripts scammers reuse. These patterns come straight from FTC and BBB case descriptions and our own reported-scam data.
Honest limits: Scammers rewrite scripts; a clean message is not a clean listing.

Property risk data layers

Source: FEMA flood zones, NOAA storm history, FBI UCR crime data, HUD fair-market rents, TEA school ratings, US Census data, and city permit portals.
What it catches: Risks that do not show up in a listing: flood exposure, storm history, unpermitted work, and rents priced suspiciously below the HUD fair-market baseline.
Honest limits: Coverage depends on what each public source publishes per address; where a source has no data we show nothing rather than estimate.

Frequently asked questions

How does RemotePropView verify that a DFW property actually exists?

Two independent checks must agree before we reject an address: the street must fail to resolve at street level on mapping data AND the county appraisal district must have no parcel record at that address. When both agree, we flag the address as very likely nonexistent. When either source errors, we fail open and keep checking other signals rather than guessing.

How do you check who really owns a rental property?

We look up the owner of record in the live county appraisal district data for Dallas, Tarrant, Collin, and Denton counties, then compare that name against the person asking for money. A mismatch is shown with the real owner of record so a renter can ask the obvious question before wiring a deposit.

What makes a rental listing get flagged as a likely scam?

Hard signals: the contact is on the community blocklist as confirmed, the address has no county record and does not check out on the map, or the listing link is flagged for phishing or malware. Softer signals that raise the risk score: wire-transfer or gift-card demands, deposits before viewing, overseas-owner stories, a listing site domain registered within 90 days, disposable email addresses, and photos matching previously reported scam listings.

Can a legitimate listing be flagged by mistake?

Yes, and the design assumes it. Every warning explains what was found and what to verify; single soft signals never produce a "scam" verdict on their own. Owners and agents can dispute community blocklist entries, and disputes go to a moderator, not an algorithm.

What does RemotePropView do when a check cannot run?

We say so. If a data source is down or out of quota, the result reads "could not fully verify" instead of a false "looks clear". A missing check is never counted as a passed check.

See it work on a real listing

Paste a listing, address, or landlord message and watch these checks run. Free, no account required.

Run a free scam check

Cite this page? See the press kit and the DFW Rental Scam Report 2026.